eBus Files

eBus 6.0.0 Downloads


________________________________________________________________________________
*** ATTENTION ***

      As of this release, eBus is now based on Java 11.
      eBus does *not* use modules at this time. Therefore include
      eBus jars in -classpath and not -modulepath.

      The eBus license also converted from LGPL 2.1 to
      Apache License 2.0. The reason for the license change is
      due to Apache License 2.0 being more end-user friendly that
      LGPL 2.1.

________________________________________________________________________________


Release 6.0.0 provides the following changes:

  + Moved eBus from Java 1.8 to Java 11 but without modules.
    Place eBus jar files into -classpath and not -modulepath.

    (SF feature request #16)

  + Changed eBus license from LGPL 2.1 to Apach 2.0.
    This was done to make eBus more widely acceptable due to some
    hesitance to use open source projects using LGPL.

  + Added net.sf.eBus.net.AsyncSecureDatagramSocket class.
    Uses DTLS to connect two peer secure datagram sockets.
    Note that this security is used only when connecting datagram
    sockets. If AsyncSecureDatagramSocket is not connected to a
    peer then packets are transmitted to a target address in the
    clear like AsyncDatagramSocket.

    Since a datagram socket may only be connected to a single
    peer datagram socket this means that, if multiple secure
    datagram socket connections are required, then one
    AsyncSecureDatagramSocket is needed for each connection.

    (SF feature request #19)

  + eBus may now use secure datagrams to connect to a peer eBus
    application. This is similar to secure TCP connection already
    provided.

    (SF feature request #20)

  + Java properties-based eBus configuration is now removed from
    net.sf.eBus.config.EConfigure and
    net.sf.eBus.config.ENetConfigure classes. Command line option:

      -Dnet.sf.eBus.config.configFile=<file path>

    is no longer supported. Users are now required to more to
    JSON typesafe-based configuration files and use the command
    line option:

      -Dnet.sf.eBus.config.jsonFile=<file path>

There are four download folders:

+ Library: contains the eBus API jar files.

+ Documentation: contains the eBus Programmer's Manul in PDF and
          Javadoc folders in tar, gzipped and zip formats.

+ Source Code: snapshot of eBus maven project files at release
          time.

+ Tools: contains the eBus GUI application and configuration file
          needed to run the application.

NOTE: eBus release >= 6.0.0 requires Java 11.